Hexatron Ormand
Aperture Space
New Eden Industrie Alliance
14
   |
Posted - 2013.07.22 13:54:00 -
[1] - Quote
I am getting the socked closed error since the odyssey release. I play since august last year and never had any trouble till odyssey was released.
I can confirm that the socked closed happens with and without steam - as i suspected that as a reason myself and started eve without steam several times, but had the same result: a socket closed error.
I can furthermore confirm that it seems not to be connection or ISP based cause i run 2 different machines, and one runs fine all the time, the other gets socket closed errors all the time since odyssey. Just to make sure i also exchanged all cables on my end, to make sure it is no problem of that. Both connections are wire/cable based, so it is no wireless issue either.
As the one machine runs super fine for hours without any trouble, uses the same ISP (obviously) and the same router, i would pretty much say i can exclude those from being the trouble makers.
So why does it run fine for a year.. odyssey comes out.. and i have socket cloed errors? On one machine and not the other? Definately no ISP/router issue at all!! Otherwise both my machines would get kicked out at the same time (as they are also in the same system, using the same "part of the cluster server").
The always running machine still uses old windows xp with a 32bit OS, the other one runs windows 7 in a 64bit version.
The issue seemed to be solved for some time when i was running my EVE client in admin modus on the windows 7 version, i could play several days without issues. Then Odyssey was patched, and the issues returned. Could not get rid of them since. They can be pretty annoying as they hit randomly without any warning. Not all too nice if you fly through hostile territory (as i did to take the screenshots of "steve" for the sanctuary image contest - had the socket closed at least 4 times on that route... it for sure caused super huge adrenaline rushes.. lol
Ok back on topic and some ideas/hints:
- I have been wondering if a localized client could cause trouble in whatever way? Many of my corpmates who all use the localized client have the same trouble
- Some right/service conflicts with windows 7 maybe, as my XP machine seems to run fine. Also cause i was able to fix the issue for some time with using admin mode on windows 7 - unfortunately it is now back even with admin mode. Are windows 7 network quality services maybe more time critical? Or causing the network packets to behave differently than on windows xp machines?
- I heard one of my corpmates say that adding fleetmembers to the watchlist caused him to get socket closed errors all the time. Since he is not using this feature anymore, he is not getting socket closed errors anymore. So maybe it is just specific data or the client side interpretation of it?
- as noted by someone else before in this thread, i also always get 2 socked closed error windows whenever it occurs
Wish i could provide a lot more information - but i think confirming that it may NOT be isp/router/connection based at all, may bring the research in a different direction, and may help finding its actual source.
|